Asynchronous load of source dependencies

ABSTRACT

Asynchronous loading of source dependencies is disclosed. An indication is received in the course of executing a script that a source file on which a current class or function depends is not available, wherein the current class or function is called or executed during the execution of the script. Execution of remaining portions of the script, if any, that do not depend on the source file, continues, or other processing tasks are performed if no such portions remain, while the source file is loaded asynchronously.

CROSS REFERENCE TO OTHER APPLICATIONS

This application is a continuation of co-pending U.S. patent applicationSer. No. 11/811,020 (Attorney Docket No. P5461US1) entitled ASYNCHRONOUSLOAD OF SOURCE DEPENDENCIES filed Jun. 8, 2007 which is incorporatedherein by reference for all purposes.

BACKGROUND OF THE INVENTION

Web page and web application developers use scripting languages, such asJavaScript™, to provide dynamic behavior in a web page. For example, inresponse to a user input a script embedded and/or referenced in a pagemay be run and the result used to modify the display, e.g., to displayoutput data, or to provide other dynamic behavior. Scripts not embeddedstatically in a page typically are loaded as source files (e.g., a .jsfile in the case of JavaScript).

A JavaScript or other source file may define a function, such as afirst-class function, that behaves or can be made to behave similarly toa software object written using a true object-oriented programminglanguage (OOPL or OOL). Such an “object” referenced in a page may haveone or more “dependencies”; i.e., to execute properly one or more otherobjects (source files) must be present and initialized. Using typicalprior art approaches—for example, Dojo and other techniques that employXMLHttpRequest or similar objects, commands, and/or interfaces—suchsource dependencies are loaded synchronously, leading to a serializationof loads which may result in a significantly slower user experience. Forexample, a page may wait to load and/or client side application or othercode may wait to execute or continue executing until a required objectand all its dependencies have been loaded.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 illustrates an embodiment of a network environment.

FIG. 2 is a flow chart illustrating an embodiment of a prior art processfor loading source files.

FIG. 3 is a flow chart illustrating an embodiment of a process forcreating a page at a client, based on components retrieved from aserver, including by loading asynchronously any required source filesand/or dependencies thereof.

FIG. 4 is a flow chart illustrating an embodiment of a process forlinking a source file to a component and/or page.

FIG. 5 is a flow chart illustrating an embodiment of a process forimporting one or more source files.

FIG. 6 is a flow chart illustrating an embodiment of a process forimporting a source file.

FIG. 7 is a flow chart illustrating an embodiment of a process fordefining a class/function programmatically at a client.

FIG. 8 is a flow chart illustrating an embodiment of a process forincluded inherited attributes into a class/function definition beinggenerated programmatically at a client.

FIG. 9 is a flow chart illustrating an embodiment of a process forgenerating programmatically a pointer to a super implementation of anoverwritten method.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess, an apparatus, a system, a composition of matter, a computerreadable medium such as a computer readable storage medium or a computernetwork wherein program instructions are sent over optical orcommunication links. In this specification, these implementations, orany other form that the invention may take, may be referred to astechniques. A component such as a processor or a memory described asbeing configured to perform a task includes both a general componentthat is temporarily configured to perform the task at a given time or aspecific component that is manufactured to perform the task. In general,the order of the steps of disclosed processes may be altered within thescope of the invention.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Asynchronous loading of source dependencies is disclosed. An indicationis received in the course of executing a script that a source file onwhich a current class or function depends is not available. Execution ofremaining portions of the script, if any, that do not depend on thesource file, continues, or other processing tasks are performed if nosuch portions remain, while the source file is loaded asynchronously. Insome embodiments, import functions configured to provide callbacks tomethods of a class definition function are used to enable sourcedependencies to be loaded asynchronously. In this way, the classdefinition function can complete execution from a JavaScript enginestandpoint even if a super-class on which the class that is beingdefined depends is not yet available.

FIG. 1 illustrates an embodiment of a network environment. In theexample shown, a client 102 communicates with a server 104 via a network106. Network 106 corresponds to any public or private network, such as aLAN, WAN, the Internet, etc., and facilitates the communication andinterchange of information between client 102 and server 104. A database108 is employed by server 104 to organize and store content. Client 102may desire to access content and/or a software program or applicationavailable from server 104. For example, it may be desirable by client102 to access a web page, web site, or a web-based application hosted byserver 104. A page or other content hosted by server 104 may berequested by client 102, for example, by entering an associated URL intoa browser, via an HTTP GET request, via an associated hyperlink, via adedicated client-side program, etc. In response, in some embodiments, anat least initial definition associated with the desired page or otherrequested content is provided to client 102 by server 104. The page mayinclude or reference one or more JavaScript scripts and/or source files,e.g., configured to provide dynamic behavior at the client. Such scriptsmay be stored in a database such as database 108 and/or in a file systemon server 104, and client 102 may be required to retrieve such sourcefiles from the server 104 in order to obtain script code desired to beexecuted (or available for execution) at the client 102.

As previously mentioned, a web page may include or reference scriptsthat implement the logic or dynamic behavior associated with the page.Such scripts may be embedded within or referenced in the HTML file andtypically are programmed using a procedural and/or prototype-basedlanguage, such as JavaScript. In some embodiments, it is useful to makea scripting language at least in part mimic aspects of object orientedbehavior so that useful characteristics of the object oriented paradigmsuch as encapsulation and reuse can be acquired. This can beaccomplished, for example, by defining appropriate declarations andfunction definitions using the syntax and constructs of the scriptinglanguage. Although JavaScript is described in the examples herein,similar techniques can be employed with any other appropriate scriptinglanguage. As used herein, a JavaScript “class” actually comprises aJavaScript function implemented in a manner that at least in part allowsthe function to mimic the functionality of a class in an object orientedparadigm. In some embodiments, the encapsulation of the scriptsassociated with a page and/or components of the page facilitates theseparation of the display layer (e.g., the HTML elements) and the logic(e.g., the scripts) of the page. Since different groups of people may beassociated with coding the display layer (e.g., graphic designers) andthe logic (e.g., web developers) associated with a page, in someembodiments, it is useful to separate the logic from the display layerof the page as further described herein to reduce the risk of errorsthat may arise from multiple groups or people contributing to the codingof a particular page or an associated application.

FIG. 2 is a flow chart illustrating an embodiment of a prior art processfor loading source files. A process such as the one shown in FIG. 2 maybe used, for example, to retrieve from a server JavaScript (.js) sourcefiles referenced by or otherwise required to render a web page. An“import” or similar function is invoked to retrieve the required sourcefile(s) (202). Other processing is blocked while the source file isretrieved and loaded (204). The required source files, including anyrequired dependencies, are obtained and loaded (206). Once all requiredsource files, included all dependencies, have been loaded (208), anindication is provided that the source file(s) have been retrieved andloaded and the previously blocked processing is allowed to resume (210).Under the prior art approaches, such as the one illustrated in FIG. 2,the processing required to actually render the page and/or to be morenearly ready to render the page, once the required source files havebeen retrieved and loaded, is blocked from executing until all therequired source files, including all dependencies, have been loaded. Asa result, if required source files have a lot of dependencies, or if thesource files (e.g., super-classes) on which a required source filedepends have further dependencies, etc., further processing of the pagemay be blocked while a serialization of source file loads occurs, untilall required source files and dependencies have been loaded, only afterwhich will the browser and/or script engine continue to perform theprocessing required to render the page.

Asynchronous loading of source file dependencies is disclosed. In someembodiments, a function is provided that programmatically generates atthe client a class/function definition for a required class/function.The definition is based in some embodiments on a template, declaration,or other input provided by a web application developer. If a sourcedependency, e.g., a super-class, is encountered and determined not to bepresent, a method associated with the function that generates theclass/function definition registers with the function tasked withimporting the source file on which the class/function being defineddepends for a callback to a method that will allow definition of thecurrent class/function to resume once the source file on which itdepends has been loaded. The callback technique allows other processingto continue while source dependencies are loaded. Once the sourcedependencies have been loaded, which implies that any source on whichsuch source dependencies having been loaded, programmatic generation ofthe class/function definition is completed and the class/function isready to execute. This approach allows other processing, e.g., renderingof portions of a page that are ready to be rendered, to continue whilesource dependencies are loaded asynchronously.

FIG. 3 is a flow chart illustrating an embodiment of a process forcreating a page at a client, based on components retrieved from aserver, including by loading asynchronously any required source filesand/or dependencies thereof. In some embodiments, a component basedapproach is used to enable web pages to be created dynamically at theclient, e.g., based on XHTML templates, associated logic (e.g.,JavaScript classes/functions), and binding declarations indicating therelationship between logic objects (classes/functions) and the displayelements with which they are associated. In some embodiments, logicincluded and/or referenced in a component, such as a JavaScriptclass/function, may be required to be retrieved from a server. In somecases, such required code may include source dependencies, e.g., asuper-class, that may also have to be retrieved from the server to beable to render the component/page. In the example shown in FIG. 3, acomponent is received at the client, e.g., from a server in response toa request sent by the client to the server to obtain the component(302). The component is parsed (304). In some embodiments, the componentcomprises an XHTML or other file that comprises or references a scriptsource (for example, a .js) file required to render the component. Ifthe component includes a script tag or other declaration linking asource file to the component (306), a “Link” or import function isexecuted to cause the source file to be obtained and anyclasses/functions identified and/or declared in the source file to beloaded (308). If during the course of retrieving any such class/functionit is determined that the class/function has a source dependency on aclass/function or other code that is not present, the import function iscalled recursively for each such dependencies until all required files,including all dependencies, have been loaded and initialized. In theexample shown, the component received at 302 may include or indicate asource dependency apart from source files linked explicitly to thecomponent. For example, in some embodiments a component may include oneor more binding declarations binding an identified class/function and/orone or more variables thereof to a display element associated with thecomponent. If no such further dependencies are included in the component(310), or once any further source files on which the component dependshave been loaded (310, 312, 314), the component is rendered (316). Insome embodiments, rendering of the component begins only after thelinked source file, if any, has been fully loaded and initialized. Insome embodiments, asynchronous loading of source dependencies asdescribed herein may make it possible to begin rendering a component, orportions thereof, or to begin or continue rendering other components orportions of the page, prior to all source files required for thecomponent, including all dependencies, have been loaded and initialized.

FIG. 4 is a flow chart illustrating an embodiment of a process forlinking a source file to a component and/or page. In the example shown,a toolkit or other set of files loaded onto the client, e.g., downloadedto the client from a web application server, includes a predefinedfunction, named “Link” in this example, configured to hold arguments tobe passed to an “Import” function once that function has been downloadedto the client and initialized. This technique enables an initial page tobegin loading and possibly being rendered while the linked file(s)is/are obtained, parsed, and executed, even if the “Import” function hasnot yet been downloaded and initialized. If the Link function is called(402), it determines whether the “Import” function is present (404). Ifso, the Link functions passes to the Import function the argumentsprovided originally to the Link function (406). Otherwise, the Linkfunction stores the file name(s) passed to it as arguments (405) untilsuch time as the Import function is available (404), at which time itpasses the file name(s) to the Import function (406). In variousembodiments, the Import function includes methods and/or other logic todetermine whether required classes are already present at the client,and if not to obtain such classes from the server, including by loadingany source dependencies asynchronously, as described herein.

FIG. 5 is a flow chart illustrating an embodiment of a process forimporting one or more source files. A call to an import function, named“Import” in this example, is received (502). In various embodiments thecall is made by a parser or engine executing code comprising a componentassociated with a page, by the Link function described above, by anotherinstance of the import class/function, and/or directly or indirectly bythe function described above that generates programmatically a classdefinition. In this example, the import function creates and executesfor each required file to be imported a corresponding instance of theimport class/function (504). Each instance so created is configured insome embodiments to retrieve the source file that the instance wascreated to retrieve. For example, in some embodiments, if the call“Import (“A”, “B”, and “C”) were received (502), three separateinstances of the import object/function would be created (504), one toretrieve file “A”, a second to retrieve file “B”, and a third toretrieve file “C”. In some embodiments each instance is configured toreport to the instance that created it once the source file (e.g.,class/function) has been loaded and initialized. In the example shown inFIG. 5, once all required files have been determined to have been loadedand initialized (506), the import function notifies the respective stubobjects (described more fully below) associated with each classassociated with the source files that have been imported (508). In theexample shown, the notification is in the form of a callback to a“complete initialization” method of such stub objects. In someembodiments, this callback indicates to the stub object (or other codeconfigured to generate a class/function definition programmatically)that its required dependencies have been loaded and initialized andtherefore are available to be used to complete the definition of theclass/function.

FIG. 6 is a flow chart illustrating an embodiment of a process forimporting a source file. In some embodiments, the process of FIG. 6 isimplemented by an import object instance created to retrieve (if notalready present) a particular source file, such as the instancesdescribed above in connection with 504 of FIG. 5. If the import objectinstance determines that the source file is not already present at theclient (602), it determines a URL to be used to request the source filefrom the server (604). In some embodiments, the URL is determined basedon a path to a root node on the server that is determined or inferredfrom files obtained previously from the server, such as an initial setof classes/functions passed to the client upon navigating to an initialpage associated with a web application. Browser and/or associated scriptengine executable code configured to retrieve the source file isgenerated (606) and provided to the browser (608), which executes thescript thereby causing the source file to be requested from the server,received, and parsed and executed by the script engine upon receipt. Invarious embodiments, the source file may include one or more of thefollowing: a call to the import function described above, e.g., toprompt the load (if not already present) of any dependencies; one ormore class/function definitions, one or more of which may include sourcedependencies; and/or one or more class/function definition templates ordeclarations, e.g., in a syntax as described below, usable to generateprogrammatically at the client a definition of a requiredclass/function. Once the source file (a required class in this example)has been determined to have been loaded (610), or if it was determinedat the outset that the class was already present at the client (602), anotification that the class has been loaded is sent (612), e.g., to acoordinating instance of the import function that was called to retrievethis and other related source files, as described above.

In some embodiments, a source file may include a class/functiondefinition, or more precisely a template or set of declarations usableto generate such a definition programmatically at the client. In someembodiments, one or more functions and/or methods are provided andassigned names that are near variants of reserved words used inclass-based object-oriented programming (OOP) languages to declare aclass, invoke inheritance (i.e., identify a super or parent class), anddefine methods and variables to be implemented by the class. In someembodiments, the function/method names differ from the correspondingreserved word by one character, such as by adding or omitting acharacter, capitalizing an initial character, etc. For example, in someembodiments a function configured to generate programmatically at aclient a class/function definition is named “Class” with a capital “C”,“Extends” with a capital “E”, and “Implements” with a capital “I”.Another example is adding an underscore or other character to thebeginning of a reserved word, such as “_class”. In some embodiments, afunction named “Class” is defined and returns a stub object to whichmethods named “Extends” and “Implements” are attached. Providing such afunction enables a developer to declare a class/function, to be definedand implemented in a prototype-based language such as JavaScript, usinga syntax that is similar to that used in class-based OOP languages withwhich the developer may be more familiar and/or which in any event maybe easier or more convenient for the developer to use. For example, if aclass/function named “Class” includes (or returns an object/functioninstance that includes) methods “Extend” for inheritance and“Implements” for defining class behaviors/variables, a developer candeclare a class/function using syntax such as “Class( ).Extends().Implements({ })”, with the argument of the Class function being thename of the class/function desired to be defined at the client, theargument of the Extends function/method indicating a class/function theparameters (methods and/or variables) of which it is desired that theclass/function being defined inherit, and the arguments of theImplements method including the methods and variables to be implementedby the class/function to be defined programmatically at the client.

FIG. 7 is a flow chart illustrating an embodiment of a process fordefining a class/function programmatically at a client. A class/functiondeclaration in a form such as “Class( ).Extends( ).Implements({ })” isencountered (702), e.g., in the course of parsing a component and/or aretrieved source file as described above. The “Class” function is called(704) and returns a stub object (706) having methods that include amethod named “Extends” and a method named “Implements”. If theclass/function declaration included an “Extends” declaration (708), the“Extends” method of the stub object is executed (710) with respect tothe super-class named in the argument of the “Extends” declaration. Oncethe “Extends” method and any associated methods have finished (712),indicating in this example that the super-class is fully loaded and themethods and variables of the super-class have been incorporatedprogrammatically into the definition of the class/function beingdefined, the “Implements” method is invoked (714). In some embodiments,the “Implements” method iterates through the arguments provided to itand adds each to the class/function definition as a method/function orvariable, as appropriate. Once the implements method (and/or any relatedor internal method) is done (716) the class/function definition iscompleted and the process ends. In some embodiments, once the Extends(if applicable) and Implements methods have finished, the stub tells theinstance of the import class/function described above that theclass/function is fully loaded and initialized and the class itselfsends a load event which will triggers callbacks within other objectsobserving that class for the load event.

FIG. 8 is a flow chart illustrating an embodiment of a process forincluded inherited attributes into a class/function definition beinggenerated programmatically at a client. In some embodiments, the processof FIG. 8 is implemented by an “Extends” method and/or related methodsof a function such as the “Class” function described above. In theexample shown, it is determined whether the super-class the name ofwhich was provided as an argument to the Extends method is present atthe client and initialized (802). If the super-class is defined at theclient (806) and is fully loaded and initialized (812), initializationis completed (818). In some embodiments, if the super-class isdetermined to be present and ready initialization is completed by thestub itself calling its own “complete initialization” method. In someembodiments, when the “complete initialization” method is invoked andthere is a super-class, the “complete initialization” method setsinheritance in place and passes the arguments of the “Implements”portion of the class definition to the “Implements” method of the stub.If the super-class is not yet defined at the client (806), the stubobject registers itself with the import function instance configured toretrieve the super-class for a callback to an “import load callback”method of the stub object to be made when the import function determinesthat the super-class has been retrieved (808). Once the callback isreceived (810), it is determined whether the super-class is ready (812).If so, the “complete initialization” method is called by the stubitself, for example by the “import load callback” method that receivedthe callback indicating that the super-class had been retrieved. If thesuper-class is determined to not be ready (812), for example because thesuper-class has a source dependency that is not yet satisfied, the stubregisters itself to receive a callback when the super-class is ready(814), e.g., for a callback to its “complete initialization” method.Once the latter callback is received (816), initialization is completed.

In some embodiments, the use of callbacks as described above allows thefunction “Class” to be considered finished being executed, from aJavaScript engine perspective, even if the super-class (or some othersource dependency) is not yet present and/or ready. This is so becauseif the super-class is not available the stub object registers for itscallback from the import function while the JavaScript (or other script)engine finishes executing the instructions comprising the Class functionand moves on, allowing the browser and JavaScript engine to continuewith other tasks while the super-class is retrieved and initialized,which as noted above may require that classes on which the super-classdepends to be retrieved, etc.

In some cases, a web application developer or other programmer maydesire to invoke a method as it was defined prior to being overwrittenin a current function/class. In class-based OOP environments, thistypically is done by invoking the “super” method. Since class-based OOPlanguages have a native concept and understanding of a class hierarchy,it is easy for the super method to find and execute the superimplementation of the method. However, in a language that insteadprovides prototype-based inheritance, such as JavaScript, there is noclass hierarchy and therefore no native ability to invoke a superimplementation of an overwritten method. Instead, a programmer must beaware of the hierarchy of classes/functions he/she has created and mustinclude manually in a function definition, for example, a pointer to asuper implementation of a method he/she wishes to invoke. Providing afunction that generates and inserts such a pointer programmatically isdisclosed.

FIG. 9 is a flow chart illustrating an embodiment of a process forgenerating programmatically a pointer to a super implementation of anoverwritten method. In the example shown, an argument (e.g., a method orfunction declaration) in a form such as “_super.functionName( )” isencountered (902). In some embodiments, “_super” is a functionconfigured to implement the remaining steps of the process of FIG. 9. Invarious embodiments the function has a name that is a near variant ofthe reserved word super, e.g., an additional character; an omittedcharacter; an underscore character preceding the word “super”;capitalization of a letter in the word “super”; and capitalization ofthe first letter in the word “super”. A current location in the “class”hierarchy, e.g., the current function name or other identifier, isstored as the start location for the current iteration of the process ofFIG. 9, e.g., the current iteration of the function “_super” (904).Starting at the super-class of the current class (906), it is determinedwhether the function/method was last overwritten (or first defined, ifnot previously overwritten) at this level (908). If not, processingcontinues at the next level up from the current level, i.e., thesuper-class of the class just examined (910). Once the class/level inwhich the function/method was last overwritten (or first defined, ifapplicable) (908), a pointer from the starting point stored at 904 tothe super implementation is constructed (912). In some embodiments, thepointer is inserted programmatically in the definition and/or in aninstance of the function/method in which the “_super” function/methodwas invoked, for example in place of the function/method name “_super”.This approach relieves the programmer of the need to construct manuallya pointer to the super implementation, which consumes time and may leadto error, particularly in more complex applications that involve manyfunctions and/or a complicated hierarchy.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A method of loading source files, comprising:receiving, in the course of executing a script, an indication that asource file on which a current class or function depends is notavailable, wherein the current class or function is called or executedduring the execution of the script; and continuing execution ofremaining portions of the script, if any, that do not depend on thesource file, or continuing on to other processing tasks if no suchportions remain, while the source file is loaded asynchronously.
 2. Amethod as recited in claim 1, wherein the indication that the sourcefile is not available comprises an indication that the source file isnot available at a client.
 3. A method as recited in claim 1, whereinthe source file is loaded from a server.
 4. A method as recited in claim1, wherein the source file comprises a super-class or function of thecurrent class or function.
 5. A method as recited in claim 1, whereinthe source file comprises a first source is file and further comprisingreceiving, in the course of loading the first source file, an indicationthat the first source file depends on a second source file that is notavailable.
 6. A method as recited in claim 1, wherein the indicationthat the source file is not available comprises an indication that thesource file has not been retrieved from a server.
 7. A method as recitedin claim 1, wherein the indication that the source file is not availablecomprises an indication that the source file has been retrieved from aserver but has not been initialized.
 8. A method as recited in claim 1,further comprising receiving an indication that the source file has beenloaded.
 9. A method as recited in claim 8, wherein the indication thatthe source file has been loaded comprises a callback.
 10. A method asrecited in claim 9, wherein the callback is triggered by a load event.11. A method as recited in claim 9, wherein the callback is sent by animport function configured to retrieve the source file.
 12. A method asrecited in claim 9, further comprising registering for the callback. 13.A method as recited in claim 9, wherein the callback is to a method ofan object or function configured to generate programmatically adefinition for the current class or function.
 14. A method as recited inclaim 8, further comprising executing a portion of the script thatdepends on the source file.
 15. A method as recited in claim 14, whereinthe portion of the script that depends on the source file comprises amethod that includes programmatically in a definition of the currentclass or function the methods and variables of a super-class with whichthe source file is associated.
 16. A method as recited in claim 1,wherein the script comprises a function configured to generateprogrammatically a definition of the current class or function.
 17. Aclient computer system, comprising: a communication interface; and aprocessor coupled to the communication interface and configured to:receive, in the course of executing a script, an indication that asource file on which a current class or function depends is notavailable, wherein the current class or function is called or executedduring the execution of the script; and continue execution of remainingportions of the script, if any, that do not depend on the source file,or continuing on to other processing tasks if no such portions remain,while the source file is loaded asynchronously from a server via thecommunication interface.
 18. A system as recited in claim 17, whereinthe processor is further configured to request the source file from theserver.
 19. A system as recited in claim 17, wherein the processor isconfigured to execute the script in the context of a browser softwarerunning on the client computer system.
 20. A computer program productfor loading source files, the computer program product being embodied ona computer readable medium and comprising computer instructions for:receiving, in the course of executing a script, an indication that asource file on which a current class or function depends is notavailable, wherein the current class or function is called or executedduring the execution of the script; and continuing execution ofremaining portions of the script, if any, that do not depend on thesource file, or continuing on to other processing tasks if no suchportions remain, while the source file is loaded asynchronously.